Summary

Fixes chefspec#980 — .with(source: <matcher>) never matches.

ResourceMatcher#matches_parameter? special-cases the source property:

if parameter == :source
  # Chef 11+ stores the source parameter internally as an Array
  Array(expected) == Array(value)

The intent is to let a plain string match a source that Chef stored as an Array. But wrapping the expectation in an Array and comparing with == means an RSpec matcher or Regexp can never match. For the reporter's case:

.with(source: end_with('MyFile.pem'))   # value is "C:/MyFile.pem"
# becomes: [#<EndWith ...>] == ["C:/MyFile.pem"]  => always false

Every other property routes through expected === value, which is exactly what makes matchers/Regexps work — source was the one exception.

Fix

Try expected === value first (so RSpec matchers, Regexps, and exact scalar/array values all work), then fall back to the array-normalized Array(expected) == Array(value) so a plain string still matches a single-element array source — preserving the original behavior.

expected === value || Array(expected) == Array(value)

Testing

• Added unit specs for :source matching (TDD — the matcher and Regexp cases failed first): exact string, plain-string-vs-array, exact array, an RSpec matcher against a scalar source (the issue), a Regexp, and a non-matching matcher (stays false — no over-matching).
• bundle exec rspec spec/unit/ → 167 examples, 0 failures.
• Acceptance examples for the real source-using resources (cookbook_file, remote_file, template, render_file) → 116 examples, 0 failures (array-source path unregressed).
• cookstyle --chefstyle -c .rubocop.yml → no offenses.

Note

Touches spec/unit/matchers/resource_matcher_spec.rb, which is also rewritten by #31 and #42. Whichever merges first, the others need their describe blocks combined into the one file.